> For the complete documentation index, see [llms.txt](https://kerneldao.gitbook.io/kernel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerneldao.gitbook.io/kernel/getting-started/kernel-deprecated/kernel-points-guide.md).

# Kernel Points Guide

What are Kernel Points?

Kernel Points are a measurement system that rewards users for depositing assets into the Kernel ecosystem. 

### Point Conversion Rates

#### Basic Conversion

* 1 Kernel Point = 1 Kelp Grand Mile = 1000 Kelp Miles<br>

### Daily Point Allocation

Points are allocated daily based on your deposit amounts:

* **BNB Deposits**:
  * 1 BNB deposited = 2 Kernel Points per day
  * (Approximately 0.5BNB = 1 Kernel Point per day)
* **BNB LST Deposits**:
  * 1 BNB deposited = 2.2 Kernel Points per day
  * (Approximately 0.45 BNB = 1 Kernel Point per day)
* **Bitcoin (BTC) Deposits**:
  * 1 BTC deposited = 260 Kernel Points per day
  * (Approximately 0.003846 = 1 Kernel Point per day)
* **rsETH deposits**
  * 1 rsETH  deposited = 10 Kernel Points per day
  * (Approximately 0.1 = 1 Kernel Point per day)

### Examples

#### Daily BNB Point Calculations

If you deposit 10 BNB:

* Daily Points: 10 BNB × (2 points/BNB) = 20 Kernel Points per day
* Weekly Points: 20 × 7 = 140 Kernel Points
* Monthly Points (30 days): 20 × 30 = 600 Kernel Points

#### Daily BNB LSTs Point Calculations

If you deposit 10 BNB:

* Daily Points: 10 BNB × (2.2 points/BNB) =22 Kernel Points per day
* Weekly Points: 22 × 7 = 154 Kernel Points
* Monthly Points (30 days): 22 × 30 = 660 Kernel Points

#### Daily BTC Point Calculations

If you deposit 0.5 BTC:

* Daily Points: 0.5 BTC × (260 points/BTC) = 130 Kernel Points per day
* Weekly Points: 130 × 7 = 910 Kernel Points
* Monthly Points (30 days): 130× 30 = 6900 Kernel Points

#### Daily rsETH Point calculations

If you deposit 1 rsETH:

* Daily Points: 1 rsETH × (10 points/rsETH) = 10 Kernel Points per day
* Weekly Points: 10 × 7 = 70 Kernel Points
* Monthly Points (30 days): 10 × 30 = 300 Kernel Points

### Quick Reference Table

| Deposit Amount | Daily Kernel Points |
| -------------- | ------------------- |
| 1 BNB          | 2 points            |
| 10 BNB         | 20 points           |
| 1 BNB LST      | 2.2 points          |
| 10 BNB LST     | 22 points           |
| 1 BTC          | 260 points          |
| 0.1 BTC        | 26 points           |
| 1 rsETH        | 10 points           |

### Important Notes

* Point allocation begins from the day of successful deposit confirmation
* Points accumulate continuously as long as deposits are maintained
* The daily allocation system ensures consistent and predictable reward distribution
* Points are non-transferable and tied to deposit addresses

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kerneldao.gitbook.io/kernel/getting-started/kernel-deprecated/kernel-points-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.